…ounterparts

Some functions have been adapted if v2 changed the API. Type aliases are the preferred way to convert types unless introducing an alias may leak v2 details.

We kept some types as they would expose v2 types, using manual conversion for these in the frontend functions that require them.

We kept as much tests as possible, but some were removed because they were asserting internal working no longer accessible, as v1 is an external user of v2.

…ir v2 counterparts

The original API is kept as is, wrapping around v2 equivalent code and configs, maintaining the behaviour expected by the package's tests.

…terparts

The conversion turned the API to a pure transparent frontend, with exported functions calling their v2 versions.

…parts

The conversion turned the API to a pure transparent frontend, with exported functions calling their v2 versions, including the types as v2 aliases.

The conversion turned the API to a pure transparent frontend, with exported functions calling their v2 versions.

…2 counterparts

The conversion turned the API to a pure transparent frontend, with exported functions calling their v2 versions.

Option types have been aliased, and contrib types have been used as wrappers to embed their v2 versions.

…ion for tests expecting v1's mocktracer.Span

…-contained in v1

… with v2 version

This reverts commit bd92328. Let's keep our v2 behavior and update the tests in dd-source to accomodate

…ror in TestFilterNilOptionsOnStart